Wireless Device For Voice Communication

ABSTRACT

A wireless handset for use in a peer-to-peer voice communications system comprising: a display; a keyboard comprising multifunctional keys capable of entering numeric or alphabetic characters depending on a number of key presses, said keyboard being arranged to enter contact information into a user interface displayed on said display, select contacts on the user interface, and initiate a packet data voice call with a contact; a microprocessor arranged to execute embedded client software, wherein the client software is arranged to establish a packet data voice call over the network and encode speech information as individually addressed packets; and a radio communication device arranged to transmit said individually addressed packets as radio signals from said wireless handset to a network.

RELATED APPLICATIONS

This application is a divisional of U.S. application Ser. No.11/515,411, filed Aug. 31, 2006.

The entire teachings of the above application are incorporated herein byreference.

FIELD OF THE INVENTION

This invention relates to a wireless device for voice communication,particularly for peer-to-peer communication.

BACKGROUND OF THE INVENTION

Peer-to-peer (“P2P”) communication systems allow the user of a personalcomputer (“PC”), to engage in voice communication (calls) across acomputer network such as the Internet. These systems are beneficial tothe user as they are often of significantly lower cost than traditionaltelephony networks, such as fixed line or mobile cellular networks. Thismay particularly be the case for long distance calls. These systemsutilise voice over internet protocol (“VoIP”) over an existing network(e.g. the Internet) to provide these services, although alternativeprotocols can also be used. To use a peer-to-peer call service, the usermust install and execute client software on their PC. The clientsoftware provides the VoIP connections as well as other functions suchas registration and authentication. A call may be made using VoIP inaccordance with methods known in the art, such as disclosed in WO2005/009019.

Some calls in a peer-to-peer communication service may be free to theuser, such as calls to other users of the same peer-to-peer service.There are therefore significant advantages to the user of the P2Pcommunication service compared to traditional fixed or mobile services.However, the user is constrained by the fact that, in order to make orreceive calls using a P2P communication service, they must have accessto a PC. Even if the user does have access to a PC, the user must firstswitch on the PC before making a call, and consequently wait for it toboot up before the call can be made. Additionally, if the user wishes toreceive incoming calls, they must leave the PC switched on, as otherwisecalls cannot be received. This has the disadvantage of being inefficientfrom an energy consumption perspective.

Users may also be accustomed to mobility whilst using conventionaltelephony services, due to the prevalence of cordless phones and mobilecellular networks. With P2P communication services, however, the user'slocation is restricted to the area directly around the PC running theP2P client software.

SUMMARY OF THE INVENTION

According to one aspect of the present invention, there is provided awireless handset for use in a peer-to-peer voice communications systemcomprising: a display; a keyboard comprising multifunctional keyscapable of entering numeric or alphabetic characters depending on anumber of key presses, said keyboard being arranged to enter contactinformation into a user interface displayed on said display, selectcontacts on the user interface, and initiate a packet data voice callwith a contact; a microprocessor arranged to execute embedded clientsoftware, wherein the client software is arranged to establish a packetdata voice call over the network and encode speech information asindividually addressed packets; and a radio communication devicearranged to transmit said individually addressed packets as radiosignals from said wireless handset to a network.

In one embodiment, the individually addressed packets comprise voiceover internet protocol (VoIP) packets.

Preferably, the wireless handset further comprises a storage device forstoring contact information, whereby, upon activation of the wirelesshandset, the contact information is transmitted to the wireless handsetfrom a contact server connected to said network and stored in saidstorage device.

In another embodiment, the user interface further displays presenceinformation for the contacts, said presence information indicating thecurrent status of the contact.

In another embodiment, the user interface further displays a contactsearch interface, whereby information is entered into the contact searchinterface using the keyboard and, in response thereto, themicroprocessor is arranged to create a contact search request that istransmitted to the network by said radio communication device.

Preferably, in response to the contact search request, a contact searchresponse is received by said radio communication device, said contactsearch response being displayed on said user interface. Preferably, apacket data voice call may be established with a contact displayed insaid contact search response. Preferably, a contact displayed in saidcontact search response may be stored in the wireless handset.

According to another aspect of the present invention, there is provideda peer-to-peer voice communications system comprising: a wirelesshandset comprising: a display; a keyboard comprising multifunctionalkeys capable of entering numeric or alphabetic characters depending on anumber of key presses, said keyboard being arranged to enter contactinformation into a user interface displayed on said display, selectcontacts on the user interface, and initiate a packet data voice callwith a contact; a microprocessor arranged to execute embedded clientsoftware, wherein the client software is arranged to establish a packetdata voice call over the network and encode speech information asindividually addressed packets; and a radio communication devicearranged to transmit said individually addressed packets as radiosignals from said wireless handset to a network; and a network elementconnected to the network and arranged to communicate with said wirelesshandset, wherein the network element transfers the individuallyaddressed packets between said wireless handset and the network.

In one embodiment, the individually addressed packets comprise voiceover internet protocol (VoIP) packets.

Preferable, the peer-to-peer voice communications system furthercomprises a contact server connected to the network for storing thecontact information for the wireless handset, wherein, upon activationof the wireless handset, the contact information is transmitted to thewireless handset via the network element and stored in said wirelesshandset.

In another embodiment, said packet data voice call is established with auser terminal connected to said network.

Preferably, the peer-to-peer voice communications system furthercomprises a gateway element connected between said data network and apublic switched telephone network, wherein said packet data voice callis established with a user terminal connected to said public switchedtelephone network.

According to another aspect of the present invention, there is provideda peer-to-peer voice communications system comprising: a wirelesshandset for making a packet data voice call to a user terminal connectedto a network, said user terminal being associated with contactinformation stored in said wireless handset; a network element connectedto the network and arranged to communicate with said wireless handset,wherein the network element transfers packet data between said wirelesshandset and the network; and a contact server connected to the networkfor storing the contact information for the wireless handset, wherein,upon activation of the wireless handset, the contact information istransmitted to the wireless handset via the network element and storedin said wireless handset.

Preferably, the peer-to-peer voice communications system furthercomprises a gateway element connected between said data network and apublic switched telephone network, wherein said user terminal isconnected to the network via said public switched telephone network andsaid gateway.

In one embodiment, the packet data voice call is a voice over internetprotocol (VoIP) call.

According to another aspect of the present invention, there is provideda handset for use in a peer-to-peer voice communications systemcomprising: a display; a keyboard comprising multifunctional keyscapable of entering numeric or alphabetic characters depending on anumber of key presses, said keyboard being arranged to enter contactinformation into a user interface displayed on said display, selectcontacts on the user interface, and initiate a packet data voice callwith a contact; a microprocessor arranged to execute embedded clientsoftware, wherein the client software is arranged to establish a packetdata voice call over the network and encode speech information asindividually addressed packets; and a communication interface arrangedto transmit said individually addressed packets from said handset to anetwork.

Preferably, the communication interface is a wired interface.Preferably, the communication interface is an Ethernet interface.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the present invention and to show how thesame may be put into effect, reference will now be made, by way ofexample, to the following drawings in which:

FIG. 1 shows a P2P communication system comprising a PC and a wirednetwork connection;

FIG. 2 shows a P2P communication system comprising a PC and a wirelessnetwork connection;

FIG. 3A shows a P2P communication system comprising a stand-alonewireless handset;

FIG. 3B shows a P2P communication system comprising a stand-alone wiredhandset;

FIG. 4 shows the functional elements of a wireless VoIP handset;

FIG. 5 shows the external controls of a wireless VoIP handset;

FIG. 6 shows a user interface when making an outgoing call to anotheruser of the P2P communication service;

FIG. 7 shows a user interface when making an outgoing call to a publicswitched telephone network (PSTN) number;

FIG. 8 shows a user interface when receiving an incoming call fromanother user of the P2P communication service; and

FIG. 9 shows a user interface when receiving an incoming call from thePSTN.

DETAILED DESCRIPTION

Reference is first made to FIG. 1, which illustrates a known P2Pcommunication system 100. A user of the P2P communication serviceoperates a computer terminal 102, such as a PC, upon which is executedclient software 104. Also connected to the PC is a handset 106, whichcomprises a speaker and microphone, to enable the user to listen andspeak in a voice call in the same manner as with traditional fixed-linetelephony. The handset 106 does not necessarily have to be in the formof a traditional telephone handset, but can be in the form of aheadphone or earphone with an integrated microphone, or as a separateloudspeaker and microphone independently connected to the PC 102.

As mentioned, the computer terminal 102 is running a client 104, whichis provided by the operator of the P2P communication service. The client104 is a software program executed on a local processor in the computerterminal 102. To initiate a call, the user can click on a contact listedfor another user displayed in the client 104, or can alternatively typein a username for the other user. The client 104 then sets up the callto the other user and the call can be made using VoIP. The clientperforms the encoding and decoding of VoIP packets.

The computer terminal 102 is connected to a modem 108, which allows thecomputer terminal to send and receive data from a network such as theInternet 110. In the example shown in FIG. 1, the computer terminal isconnected to the modem 108 using a wired connection. The wiredconnection can be, for example, Ethernet or USB.

VoIP packets from the computer terminal 102 are transmitted into theInternet 110 via the modem 108, and routed to the computer terminal 112of the other user via a modem 114. A client 116 (similar to the client104) running on the computer terminal 112 of the other user decodes theVoIP packets to produce an audio signal that can be heard by the otheruser using the handset 118. Conversely, when the other user talks intohandset 118, the client 116 executed on computer terminal 112 encodesthe audio signals into VoIP packets and transmits them, via the modem114, across the Internet 110 to the computer terminal 102. The client104 executed on computer terminal 102 decodes the VoIP packets from theother user, and produces an audio signal that can be heard by the userof the handset 106.

Alternatively, the user of the computer terminal 102 can make a voicecall to a user of a fixed-line telephone service. In this case, the usertypes in a telephone number of another user connected to the publicswitched telephone network (“PSTN”) into the client 104. The clientencodes the audio signals from the user as VoIP packets and these aretransmitted into the Internet 110 via the modem 108. The VoIP packetsare individually addressed IP packets. The VoIP packets are routed to agateway 120 connected between the Internet 110 and the PSTN 122, wherethey are converted into a form suitable for transmission across the PSTN122. The PSTN 122 delivers the converted voice information from thegateway 120 to the fixed-line telephone equipment 124 of the other user.Note that the user could also make calls to a mobile telephone via amobile network, instead of the PSTN (not illustrated in FIG. 1).

The above-described system suffers from the previously mentionedproblems that, in order for the user to make or receive phone callsusing the P2P communication service, the computer terminal 102 must bepresent and activated. If the computer terminal 102 is not activated,the user must first switch it on before making a call. Additionally, ifthere is an incoming call, for example from the fixed-line telephone 124or the computer terminal 112, then the computer terminal 102 must bepowered on in order to receive the call.

Furthermore, the users are also constrained in their mobility whilstusing the P2P communication service, due to the wired nature of theconnections between the computer terminal 102 and the modem 108, andbetween the computer terminal 102 and the handset 106.

FIG. 2 shows an alternative known P2P communication system 200. Thesystem 200 is identical to the system 100 shown in FIG. 1, except thatthe computer terminal 102 is connected to the Internet 110 via awireless connection. The computer terminal 102 has a wireless local areanetwork (“WLAN”) module with an antenna 202, which is able to transmitdata wirelessly to a WLAN access point (“AP”) 204. The AP 204 isconnected a modem 206, which is in turn connected to the Internet 110.The wireless connection can use a WLAN standard such as the IEEE 802.11family of standards (also known as WiFi). The AP 204 and the modem 206can be integrated into a single device (which may be referred to as awireless modem or wireless router), as indicated by the dashed box 208.Alternatively, they can be separate devices. The operation of the system200 shown in FIG. 2 is the same as that shown in FIG. 1 and describedabove, except that the VoIP packets from the computer terminal 102 aresent to the modem 206 wirelessly, and, similarly, VoIP packets fromother users are received at the computer terminal 102 wirelessly. Thisprovides the user with a limited degree of mobility, particularly if thecomputer terminal is a laptop or notebook computer. However, the levelsof mobility are still much lower than can be achieved with traditionalcordless phones or mobile cellular phones. This is because a laptop ornotebook computer is still of a significant size and weight, and hencehas a much lower degree of portability than the user is accustomed towith mobile and cordless telephones.

Reference is now made to FIG. 3A, in which is illustrated a P2Pcommunication system 300 comprising a stand-alone wireless handsetaccording to an embodiment of the present invention. FIG. 3A shows adedicated wireless VoIP handset 302 for making VoIP calls across theInternet without the need for a computer terminal. As the wireless VoIPhandset 302 is small enough to be hand-held, and a PC is not required,much greater levels of mobility can be achieved compared to a wirelesslaptop or notebook computer.

The wireless VoIP handset 302 connects to a wireless access point 204 ofthe same type as described above with reference to FIG. 2. In apreferred embodiment, the wireless VoIP handset 302 connects to the AP204 using an IEEE 802.11 WiFi standard. In alternative embodiments, thewireless VoIP handset 302 connects to the AP 204 using a differentwireless standard such as Bluetooth, IEEE 802.16 (WiMAX), ultra-wideband(UWB) or any other suitable wireless communications protocol.

The wireless VoIP handset 302 executes dedicated embedded clientsoftware to perform the same function as the client software 104 thatwas running on the computer terminal 102 in FIGS. 1 and 2. Inparticular, the client encodes audio signals from the user asindividually addressed VoIP packets and transmits these packetswirelessly to the Internet. Therefore, by running embedded clientsoftware on a wireless VoIP handset 302 VoIP calls can be made withoutthe computer terminal 102 being present. Embedded software means thatthe software is permanently loaded onto the device and cannot be removedby the user. However, it is still possible for the embedded software tobe upgraded or updated by the user. In addition, only approved versionsof the same software can be upgraded or updated, and the user cannotload any other type of software onto the device. Note that, in someembodiments, the embedded software can be upgraded “silently” withoutthe user knowing it is happening.

FIG. 3B shows an alternative embodiment in which is illustrated a P2Pcommunication system comprising a stand-alone wired handset. FIG. 3Bshows a dedicated VoIP handset 306 for making VoIP calls across theInternet without the need for a computer terminal. The embodiment shownin FIG. 3B is similar to that described above with reference to FIG. 3A,except that the communication between the VoIP handset 306 and the modem206 uses a wired link 308, rather than a wireless connection. Inpreferred embodiments, the link 308 between the VoIP handset 306 and themodem 206 is an Ethernet connection, although in alternative embodimentsany suitable wired communication protocol could be used, such as USB.

Reference is now made to FIG. 4, which illustrates the main functionalelements of the wireless VoIP handset 302. The wireless VoIP handset 302comprises a microprocessor (“.mu.P”) 402 (also known a centralprocessing unit (“CPU”)), which controls the operation of the wirelessVoIP handset 302 and executes embedded software. Connected to themicroprocessor is a memory 404, an optional serial interface 405, adisplay 406 (such as a liquid crystal display (“LCD”)), a speaker 408, amicrophone 410 and a keyboard 412. A radio frequency (“RF”) module 414is also connected to the microprocessor, which implements the particularradio communication standard used by the handset 302, such as WiFi. TheRF signals are transmitted and received from an antenna 416.

The speaker 408 may be connected to the microprocessor 402 via aninterface 418 which comprises audio driver hardware (including forexample amplifiers) and a digital to analogue converter. Thefunctionality of the interface 418 may alternatively be integrated intomicroprocessor. The microphone 410 is connected to the microprocessor402 via an interface 420 comprising audio receiving hardware (such asamplifiers) and an analogue to digital converter. Again, thisfunctionality may be integrated into the microprocessor 402. Thekeyboard 412 is connected to the microprocessor 402 via an encoderinterface 422. The display is connected to the microprocessor via adisplay driver interface 424. The memory 404 can include both Flash andRAM. The serial interface 405 is used for loading and updating softwareon the microprocessor 402. In preferred embodiments, the serialinterface 405 is a universal serial bus (“USB”) interface. Inalternative embodiments other serial interfaces could also be used, suchas the IEEE 1394 (Firewire) standard. In preferred embodiments, theserial interface 405 can also be used as a power source to charge thebattery in the wireless VoIP handset 302. In alternative embodiments, aseparate power supply can be used to charge the battery via a chargingconnector.

As the microprocessor 402 is operating within a battery powered handhelddevice, it needs to be of a lower processing power than the CPU inside aPC. For example, the microprocessor 402 for a handheld device cantypically have a clock speed of 200-400 MHz. In alternative embodiments,the microprocessor 402 can be complemented by a digital signal processor(“DSP”), which can perform some of the voice processing functions(described below). This allows the microprocessor 402 clock speed to bereduced, for example to 50-200 MHz.

The microprocessor 402 executes embedded software to allow the wirelessVoIP handset 302 to operate as a stand-alone VoIP device. Themicroprocessor 402 executes an operating system (“OS”) 426. In preferredembodiments, the OS 426 is Linux, although other operating systems couldalso be used. The OS 426 allows programs to be run on the microprocessor402 and controls low-level operations such as an IP stack and filesystem support.

Running on the OS 426 of the microprocessor 402 is a connection manager428. The connection manager 428 is the central component of the clientsoftware, and handles connections to the P2P communication network. Thisincludes the placing of calls, managing online status, and anycommunication with other users.

Operating under the control of the connection manager 428 is a voiceengine 430 and a power management module 432. The voice engine 430incorporates the codec for encoding and decoding the voice information.In preferred embodiments, the codec is a G.729 codec. This is used as itcan be run easily on a handheld device with a lower processing powerthan a PC. However, in alternative embodiments, any other suitable codecsuch as G.711, G.726 and wideband AMR-WB could also be used.

Apart from performing the encoding and decoding of voice information,the voice engine 430 also provides a jitter buffer, echo cancellationfacilities, voice activity detection and comfort noise generation. Thevoice engine further implements the sending and receiving of real-timeprotocol (“RTP”) packet streams, the generation of dual tonemulti-frequency (“DTMF”) tones, and the setting of output amplification(i.e. volume).

The power management module 432 allows the connection manager 428 tocontrol the power of the wireless VoIP handset 302. This is particularlyimportant for battery powered handheld devices, as a long battery lifeis necessary for the device to be user-friendly. The connection managercan request a particular power level to be used by the handset. Forexample, the power requirement can be set to “none” if the connectionmanager 428 does not have any power requirements, thereby allowing theCPU to be turned off. The power requirement can be set to “background”if the connection manager 428 is performing background tasks thatrequire a minimal level of CPU power. The power requirement can be setto “optimal” if the connection manager 428 is performing general tasks,and requires optimal processing power from the CPU. Finally, the powerrequirement can be set to “full” if the connection manager requires themaximum processing power from the CPU. Therefore, using these settingsthe connection manager 428 can control the power consumption of thehandset in order to maximise battery life.

The user of the wireless VoIP handset 302 interacts and controls theconnection manager 428 through a user interface (“UI”) 434. The UI isspecially adapted for display on the small screen of a handheld device,and is designed to be operated by a small keyboard (the structure ofwhich will be described hereinafter). Through the UI 434 of the wirelessVoIP handset 302, the user can use the P2P communication service withalmost the same level of functionality as if they were using a PC 102and a handset 106, as will now be described.

A new user of the P2P communication service can use the wireless VoIPhandset 302 to create an account and login to the P2P communicationsystem. This involves the user entering information such as their nameusing the keyboard of the wireless VoIP handset, and selecting ausername and password.

When a user has logged into the P2P communication service they canaccess their contact list on the UI of the wireless VoIP handset. Thecontact list is created by the user and is a list of people that theuser can readily set up a call with. The contact list may compriseusernames of users of the P2P communication service and regular PSTNphone numbers. In the case of contacts of other users of the P2Pcommunication service, these contacts have authorised the user to viewtheir “presence” information in the contact list. The presenceinformation is an indication of the online status of a particular user.For example, the user is able to see if a contact is online, offline,busy or away (other presence states are also possible). This informationis shown next to the contact's name in the contact list.

The user can set up a call to a contact in the contact list by, forexample, simply selecting the appropriate contact using the keyboard(note that a call to a contact can be initiated using other methods,such as from a call history or typing a username). Referring again toFIG. 3A, if a call is made to another user of the P2P communicationservice, the connection manager 428 sets up the call by transmittingdata from the RF module 414, via AP 204 and modem 206, across theInternet 110 to the destination computer terminal 112 running client 116(via modem 114). The voice call can then proceed between the user of thewireless VoIP handset 302 and the user of handset 118 in a similarmanner to that described with reference to FIG. 2.

Similarly, an incoming call from another user of the P2P communicationservice may be received at the wireless VoIP handset. In this case thecall is set up by the client 116 of the computer terminal 112. The callis received at the wireless VoIP handset 302, and can be indicated tothe user by a ring-tone, the vibration of the device, or a combinationof these (depending on user preferences). The user is also displayed theidentity of the caller on the UI, along with a picture, if this isavailable. The wireless VoIP handset has the advantage that the call canbe received without a PC needing to be present or activated.

The user of the wireless VoIP handset can set up a call to a PSTNtelephone user. This can be done by selecting a PSTN number in thecontact list (this can be associated with a contact that only has PSTNnumbers, or a contact that has both PSTN numbers and a P2P communicationservice username). Alternatively, the user can type the PSTN number intothe keyboard manually (e.g. if the number is not associated with anycontact). Referring again to FIG. 3A, the connection manager 428 makesthe call by transmitting data from the RF module 414, via AP 204 andmodem 206, across the Internet 110 to the gateway 120, where the data isare converted into a form suitable for transmission across the PSTN 122.The PSTN 122 delivers the converted data from the gateway 120 to thefixed-line telephone equipment 124 of the other user. Note that the usercan also make calls to a mobile telephone via a mobile network (notillustrated in FIG. 3A), instead of the PSTN, in a similar manner.

The user of the wireless VoIP handset can also receive incoming callsfrom the PSTN. In common with incoming calls from the P2P communicationsystem, the call is received at the wireless VoIP handset 302 and isindicated to the user by a ring-tone, the vibration of the device, or acombination of these (depending on user preferences). If CallerIDinformation is available, then this is displayed on the UI. Again, thewireless VoIP handset has the advantage that the call can be receivedwithout a PC needing to be present or activated.

As the P2P communication service operates on peer-to-peer principles,the number of central servers is kept to a minimum. In fact, the P2Pcommunication service can function almost fully without using centralservers. However, the functionality of the service can be improvedthrough the use of some central servers. For example, a central contactserver (304 in FIG. 3A) can be used to allow synchronisation of thecontact list for a user. When an existing P2P communication service userlogs in on a new device (such as the wireless VoIP handset 302), thecontact list for this user is retrieved from the central contact server304. Once it has been retrieved from the contact server 304, the contactlist is cached in the memory 404 of the wireless VoIP handset 302.Therefore, the contact list does not need to be retrieved every time theuser logs in using the wireless VoIP handset. Note that, in reality,more than one contact server 304 would be present, for redundancy andscalability reasons. However, only a single server is shown in FIG. 3Afor clarity.

In preferred embodiments, not all information for every contact needs tobe stored on the contact server 304. Only usernames, the display nameand the authorisation status are required to be stored on the contactserver 304. Other information such as the picture associated with acontact (known as the “avatar”) is obtained from the P2P communicationnetwork. In alternative embodiments, all information could be centrallystored on the contact server.

The use of a central contact server 304 allows the user to log into theP2P communication service from a variety of devices and maintain asingle unified contact list. For example, the user may use both a PC anda wireless VoIP handset at their home, and can get the same contact liston either of these devices. Furthermore, the user can also go to thehome or workplace of a different user of the P2P communication service,and use the wireless VoIP handset of the different user to log into thenetwork. The user will then have access to their own contact list, eventhough they are not the owner of the device accessing the network. Theaccess to your own contact list on any device is a significant advantageover traditional PSTN and mobile telephones.

The user of the wireless VoIP handset 302 can use the UI and thekeyboard of the device to search for the contact details of other usersof the P2P communication service. The user is presented with a dialogbox, in which they can enter details about a user they wish to searchfor (e.g. their full name or username). The wireless VoIP handset 302then retrieves this information from the network, and presents theresults to the user in the UI. In effect, this allows the wireless VoIPhandset to have access to a directory of all the users of the P2Pcommunication service directly from the device. This type offunctionality is not available on PSTN and mobile telephones, andprovides a substantial advantage to the user.

Once contacts have been found using the above-described searchfunctionality, they can be added to the contact list directly from thewireless VoIP handset. Similarly, PSTN numbers can also be added to thecontact list directly from the wireless VoIP handset. The user is alsoable to view profile information for users of the P2P communicationservice that have been found using the search or are in the user'scontact list. The profile information contains details about thecontact, including the contact's picture, which can be viewed on thewireless VoIP handset 302.

Other functionality implemented on the wireless VoIP handset 302includes: call forwarding to another number; call waiting (such that anongoing call can be placed on hold so that the user can answer anotherincoming call, and the user can flip back and forth between thesecalls); support for DTMF tones; access to voicemail (including leavingand retrieving messages, setting a custom greeting, and reverting backto a standard greeting); a call history distinguishing between missed,incoming and outgoing calls; participation in conference calls; accessto account information; and the sending and approving of authorisationrequests for contacts.

The UI of the wireless VoIP handset also provides notification ofvarious events to the user. This includes network events such asincoming calls (through notification on the UI as well as ring-tones andvibration, as mentioned previously), notification of missed calls, andnotification of voicemail messages. In addition, environmental eventsare handled and notified to the user, such as low battery alerts andwireless network signal strength.

The user of the wireless VoIP handset can configure the device tooperate with different WiFi networks. The wireless VoIP handset cansupport a range of commonly used encryption formats and a list ofpreferred networks is stored on the device. This allows the wirelessVoIP handset to operate with both secured and unsecured wirelessnetworks, and to quickly locate and connect to particular preferrednetworks (such as at the home of the user).

As illustrated in FIG. 4, the wireless VoIP handset comprises a USBserial interface 405. This interface can be used to upgrade the softwareon the wireless VoIP handset. All the software on the wireless VoIPhandset including the kernel and drivers can be updated over USB using aPC and a specific application executed on the PC. Furthermore, certainaspects of the software may be updated wirelessly over the Internetdirectly to the device, without the need to connect to a PC.

Reference is now made to FIG. 5, in which is shown an example of theexternal controls of the wireless VoIP handset 302. The front of thewireless VoIP handset 302 comprises a display 502 (such as an LCD) onwhich is displayed the UI. Below the display is a keyboard 504. Inpreferred embodiments, at the top of the device is a power button 506and at the side of the device are volume up and volume down keys 508.

The keyboard 504 comprises a left soft key (“LSK”) 510 which is used toinvoke various specific actions that are shown in the UI on the display502 directly above the LSK 510. In particular, the LSK 510 is used for“positive” actions such as “Options” and “Select”. A right soft key(“RSK”) 512 is also present that invokes actions shown in the UI on thedisplay 502 directly above the RSK 510. In particular, the RSK 512 isused for “negative” actions such as “Back” and “Clear”.

Between the two soft keys is located a navigation pad 514. Thenavigation pad can be moved up, down, left and right by the user tonavigate through the menu system and move a cursor for text entry. Thecentre of the navigation pad 514 can be depressed by the user to invokea selection. A send key 514 is present which is used to initiate a call.This key is typically coloured green. An end key 516 is present that,during an active call, ends the call, and, during an incoming call,rejects the call. This key is typically coloured red. The end key 516 isalso used to clear the content of a dialog box, and closes the dialogand returns the user to a main idle screen of the UI with subsequentpresses. Elsewhere in the UI a single press of the end key 516 returnsthe user to the idle screen. If device does not include a power key, thepower menu can be presented on the end key 516. For example, a press ofthe end key 516 for <1.5 seconds would perform the end key actionsdescribed above, a press of 1.5 to 4 seconds displays a power menu, anda press of >4 seconds switches off the device.

An alphanumeric keypad 518 is located at the bottom of the front face ofthe wireless VoIP handset. This is of a similar configuration to thatfound on a traditional mobile telephone. However, in preferredembodiments, the labelling of the keypad is adapted to the function ofthe wireless VoIP handset. In particular, because the P2P communicationsystem operates largely on names, rather than numbers, the alphanumerickeys are labelled with the letters more prominent than the numbers,whereas with traditional telephones the opposite is true.

The alphanumeric keypad 518 is used for text entry, such as adding orsearching contacts. It is also used for number entry, such as adding anddialling PSTN numbers. In particular, the keys of the keyboard aremultifunctional, such that a single key represents a number of differentcharacters. Different characters associated with a particular key may beaccessed depending on the number of key presses of the key. Some of thekeys may also be used for other features depending on the UI context inwhich they are used. For example, the “1” key can be used to accessvoicemail with a long press, the “0” key can be used to enter a space,the “*” key can be used to change text entry modes, and the “#” key canbe used to enter language symbols.

Reference is now made to FIGS. 6 to 9, in which are illustrated examplesof the user interface as different common operations are performed usingthe wireless VoIP handset. Referring first to FIG. 6, this figure showsa user making an outgoing call to another user of the P2P communicationservice, for example between the wireless VoIP handset 302 and computerterminal 112 in FIG. 3A. The UI screen shown in 602 illustrates the mainidle screen of the wireless VoIP handset. This screen shows the wirelessnetwork signal strength 604, the level of battery charge 606, the user'scurrent presence status (indicated by icon 608), the current time 610,and the amount of credit on the user's account 612. At the bottom of thedisplay are shown the labels for the soft keys LSK 510 and RSK 512. Thelabel 614 shows that if the LSK 510 is selected, the user is presentedwith a “Menu” screen. The label 616 shows that if the RSK 512 isselected, the user is presented with a “Contacts” screen.

The UI screen shown in 618 illustrates the contacts UI display that theuser is shown when the RSK 512 is selected in screen 602. Screen 618shows a list of contacts that the user has stored on the device (thesemay also have been retrieved from the contact server as describedpreviously). Each of the contacts has a name, and in this example theyare all other users of the P2P communication service, as indicated bythe icon 620 next to the name. The icon 620 indicates the presencestatus of the contact to the user. For example, the icon may indicatethat the contact is online, offline, away, busy (“do not disturb”) orany other suitable status. The LSK 510 takes the user to an “Options”screen (described hereinafter) and the RSK 512 takes the user back tothe main idle screen.

The user can use the navigation pad 514 to scroll though the list ofnames. When the user selects one of the names the wireless VoIP handsetinitiates a P2P communication service call to the selected user.

The screen 622 shows the UI display when the call to the selectedcontact is initiated. The screen 622 shows the picture 624 of the personbeing called, their name 626, and the message “Connecting . . . ” 628.The user can end the call at this stage by selecting the RSK 512, or byusing the end key 516. The screen 630 shows the UI display when the callhas been connected, and is ringing at the terminal of the contact. Thisdisplays the same information as screen 622, except the message nowshows “Ringing . . . ” 632.

When the called person picks up and the call is connected, the screenshown in 634 is displayed. This screen shows the same information asscreen 630, except that the message now reads “Call in progress” 636.The screen 634 is only displayed temporarily, typically for a fewseconds, and then the screen 638 is displayed. Screen 638 displays theduration 640 of the ongoing call and the name of the called person 642.The label for the LSK 510 is “Options” 644, and by pressing the LSK 510,the user is presented with options for handling the ongoing call, suchas putting the call on hold or muting the microphone.

The call is ended by pressing the end key 516 or my pressing the RSK512, labelled “End” 646. When the call is ended the screen 648 isdisplayed for a few seconds. This shows the same information as screen638, except that the duration is replaced by the message “Call ended”650. The UI then reverts to the main idle screen 602.

Reference is now made to FIG. 7, in which is shown the UI displays for auser making an outgoing call to a PSTN number, for example between thewireless VoIP handset 302 and fixed-line telephone 124 in FIG. 3A. Thefirst two screens 702 and 704 are identical to those shown in 602 and618 in FIG. 6 (and described above). However, in screen 704, when thedesired contact is selected the LSK 510 with the label “Options” ispressed (rather than depressing the centre of the navigation pad 514 aswas done with FIG. 6). The user is then displayed screen 708, whichshows several options for the selected contact. The user can select tocall the contact (710), send a voicemail to the contact (712), view theprofile of the contact (714), rename the contact (716), remove thecontact from the contact list (718), and block the contact from callingthe user (720).

In this example, the user selects the option to call the contact (710),and is presented with screen 722. Screen 722 lists the different methodsof communicating with the contact that the user has stored on thedevice. The screen 722 shows that the contact can be called using theP2P communication service (“Skype call” 724), using a mobile telephonenumber 726, using a home PSTN number 728 and using an office PSTN number730. The icons next to the numbers indicate their category (mobile,home, office etc.). Some contacts can, of course, have greater or fewerentries for different ways of contacting the person. In the exampleshown in FIG. 7, the user selects to call the mobile number 726 of thecontact, by depressing the centre of the navigation pad 514 or pressingthe LSK 510.

When the call to the selected number is being connected, the user isdisplayed screen 732, which shows the number being called 734 and themessage “Connecting . . . ” 736. When the telephone of the called personis ringing, the user is shown screen 738, which is identical to theprevious screen, except that the message now states “Ringing . . . ”740. When the call is answered, screen 742 is displayed. This screen isidentical to the previous screen, except that the message reads “Call inprogress” 744.

Screen 742 is only displayed for a few seconds, and the user is thendisplayed screen 746. This screen shows the duration of the call 748 andthe name of the contact 750, and is displayed until the call is ended.When the call is ended screen 752 is displayed for a few seconds. Thisshows the same information as screen 746, except that the duration isreplaced by the message “Call ended” 754. The UI then reverts to themain idle screen 702.

Reference is now made to FIG. 8, which illustrates a user receiving anincoming call from another user of the P2P communication service, forexample from computer terminal 112 to the wireless VoIP handset 302 inFIG. 3A. When the incoming call is received at the wireless VoIP handset302, the screen 802 is displayed (and the device rings/vibrates, asmentioned previously). Screen 802 displays the picture of the contact804, the name of the contact 806 and the message “Calling” 808. The usercan reject the incoming call using the end key 516 or the RSK 512, forwhich the label “Reject” 810 is displayed.

If the user accepts the call using the send key 514, the screen 812 isdisplayed. This screen is similar to the previous screen except that themessage now reads “Call in progress” 814. Screen 812 is only displayedfor a few seconds, before screen 816 is displayed. Screen 816 shows thename 818 of the caller and the duration of the incoming call 820. Whenthe call ends, the user is shown screen 822 for a few seconds. Thisscreen is similar to the previous screen, except that the duration isreplaced by the message “Call ended” 824.

Reference is now made to FIG. 9, which illustrates a user receiving anincoming call from the PSTN, for example from fixed-line telephone 124to the wireless VoIP handset 302 in FIG. 3A. When the incoming call isreceived at the wireless VoIP handset 302, the screen 902 is displayed(and the device rings/vibrates, as mentioned previously). Screen 902displays the telephone number 904 of the personal calling and themessage “Calling” 906. The user can reject the incoming call using theend key 516 or the RSK 512, for which the label “Reject” 908 isdisplayed.

If the user accepts the call using the send key 514, the screen 910 isdisplayed. This screen is similar to the previous screen except that themessage now reads “Call in progress” 912. Screen 910 is only displayedfor a few seconds, before screen 914 is displayed, which shows thetelephone number 916 of the caller and the duration of the incoming call918. When the call ends, the user is shown screen 920 for a few seconds.This screen is similar to the previous screen, except that the durationis replaced by the message “Call ended” 922.

The above-described VoIP wireless handset therefore provides a solutionto the problem of enabling VoIP calls over a P2P communication service,without the requirement to have a PC present and powered on. The VoIPwireless handset also gives the user mobility, not only within thecoverage area of the WLAN access point, but the user can also take thedevice with them when they travel, and use it to make VoIP callswherever there is WLAN coverage.

In addition, the VoIP wireless handset provides further advantages overtraditional PSTN and mobile telephones. For example, the user of theVoIP wireless handset can search for other users of the P2Pcommunication service using the VoIP wireless handset, effectivelygiving them access to a full directory direct from the handset. The usercan also log into and use a VoIP wireless handset of a different userand gain access to their personal contact list downloaded from a contactserver in the network.

While this invention has been particularly shown and described withreference to preferred embodiments, it will be understood to thoseskilled in the art that various changes in form and detail may be madewithout departing from the scope of the invention as defined by theappendant claims.

1. A peer-to-peer voice communications system comprising: a wirelesshandset comprising: a display; a keyboard comprising multifunctionalkeys capable of entering numeric or alphabetic characters depending on anumber of key presses, said keyboard being arranged to enter contactinformation into a user interface displayed on said display, selectcontacts on the user interface, and initiate a packet data voice callwith a contact; a microprocessor arranged to execute embedded clientsoftware, wherein the client software is arranged to establish a packetdata voice call over the network and encode speech information asindividually addressed packets; a radio communication device arranged totransmit said individually addressed packets as radio signals from saidwireless handset to a network; and a network element connected to thenetwork and arranged to communicate with said wireless handset, whereinthe network element transfers the individually addressed packets betweensaid wireless handset and the network.
 2. A peer-to-peer voicecommunications system as claimed in claim 1, wherein the individuallyaddressed packets comprise voice over internet protocol (VoIP) packets.3. A peer-to-peer voice communications system as claimed in claim 1,further comprising a contact server connected to the network for storingthe contact information for the wireless handset, wherein, uponactivation of the wireless handset, the contact information istransmitted to the wireless handset via the network element and storedin said wireless handset.
 4. A peer-to-peer voice communications systemas claimed in claim 1, wherein said packet data voice call isestablished with a user terminal connected to said network.
 5. Apeer-to-peer voice communications system as claimed in claim 1, furthercomprising a gateway element connected between said data network and apublic switched telephone network, wherein said packet data voice callis established with a user terminal connected to said public switchedtelephone network.
 6. A peer-to-peer voice communications systemcomprising: a wireless handset for making a packet data voice call to auser terminal connected to a network, said user terminal beingassociated with contact information stored in said wireless handset; anetwork element connected to the network and arranged to communicatewith said wireless handset, wherein the network element transfers packetdata between said wireless handset and the network; and a contact serverconnected to the network for storing the contact information for thewireless handset, wherein, upon activation of the wireless handset, thecontact information is transmitted to the wireless handset via thenetwork element and stored in said wireless handset.
 7. A peer-to-peervoice communications system as claimed in claim 6, further comprising agateway element connected between said data network and a publicswitched telephone network, wherein said user terminal is connected tothe network via said public switched telephone network and said gateway.8. A peer-to-peer voice communications system as claimed in claim 6,wherein the packet data voice call is a voice over internet protocol(VoIP) call.